System, method and apparatus for wireless sensor network configuration

ABSTRACT

A remote user can specify data collection and processing characteristics of a wireless sensor network. In one example, a configuration station enables a user to activate/deactivate different sensor channels of data to support a delivery of data streams to customers. In another example, a configuration station enables a user to specify reporting intervals for different sensor channels of data. In yet another example, a configuration station enables a user to specify transformation functions for different sensor channels of data. The remote configuration process can be applied to every sensor in every sensor module unit attached to every wireless node at a monitored location.

This application is a continuation of non-provisional application Ser.No. 14/967,832, filed Dec. 14, 2015, which is a continuation ofnon-provisional application Ser. No. 14/710,209, filed May 12, 2015,which claims the benefit of and priority to provisional application No.61/992,307, filed May 13, 2014, and to provisional application No.62/136,959, filed Mar. 23, 2015. Each of the above-identifiedapplications is incorporated herein by reference in its entirety.

BACKGROUND Field

The present disclosure relates generally to sensor applications,including a system, method and apparatus for wireless sensor networkconfiguration.

Introduction

Sensors can be used to monitor physical or environmental conditions.Wireless sensor networks can be used to collect data from distributedsensors and to route the collected sensor data to a central location.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to describe the manner in which the above-recited and otheradvantages and features can be obtained, a more particular descriptionwill be rendered by reference to specific embodiments thereof which areillustrated in the appended drawings. Understanding that these drawingsdepict only typical embodiments and are not therefore to be consideredlimiting of its scope, the disclosure describes and explains withadditional specificity and detail through the use of the accompanyingdrawings in which:

FIG. 1 illustrates an example embodiment of a wireless sensor networkthat can collect and distribute sensor information.

FIG. 2 illustrates an example embodiment of a wireless node.

FIG. 3 illustrates an example embodiment of a sensor module unit.

FIG. 4 illustrates an example embodiment of a housing of a wireless nodethat exposes connector interfaces.

FIG. 5 illustrates an example embodiment of a housing of a sensor moduleunit.

FIG. 6 illustrates an example embodiment of a wireless node that isphysically attached to a plurality of sensor module units.

FIG. 7 illustrates an example embodiment of a configuration of a set ofsensor channels between a wireless node and a sensor module unit.

FIG. 8 illustrates a framework of the relative activation of sensors inthe wireless sensor network.

FIG. 9 illustrates a framework for enabling remote configuration of theoperation of a wireless sensor network.

FIG. 10 illustrates an example embodiment of remote configuration foractivation of sensor channels of data.

FIG. 11 illustrates an example embodiment of a remote configuration of areporting interval at a monitored location.

FIG. 12 illustrates an example embodiment of a remote configuration of atransformation function for a sensor channel of data.

FIG. 13 illustrates an example embodiment of a pulse sensor.

DETAILED DESCRIPTION

Various embodiments are discussed in detail below. While specificimplementations are discussed, it should be understood that this is donefor illustration purposes only. A person skilled in the relevant artwill recognize that other components and configurations may be usedwithout parting from the spirit and scope of the present disclosure.

Sensors provide a mechanism for discovering and analyzing the state ofphysical or environmental conditions. Wireless sensor networks providean efficient mechanism for connecting with and retrieving sensor datafrom a distributed set of sensors. The growing emphasis on the Internetof Things (IoT) has further reinforced the importance of wirelessnetworks in connecting a range of devices. Notwithstanding today'semphasis on connecting a variety of devices using wirelesscommunication, it is recognized in the present disclosure that thepenetration of wireless sensor networks into the marketplace is limiteddue to the high level of installation and maintenance costs.

By their very nature, sensors are designed to measure a particularphysical or environmental condition. Sensors therefore represent a classof application-specific devices. Every sensor network installation canbe designed with unique cost constraints, measurement objectives, siterestrictions, or other application-specific requirements that caninfluence sensor network design. These application-specific qualitieslead to significant challenges in identifying a scalable solution thatcan be applied across various industries and markets. For example, it isrecognized that a scalable solution should be flexible in accommodatingnew types of sensor applications with little redesign or redeployment ofa wireless sensor network. Such a scalable solution would significantlyreduce installation and maintenance costs as new sensors and applicationfeatures are rolled out across an already deployed sensor networkinfrastructure. It is recognized that sensor network solutions shouldenable an evolution of the deployed wireless sensor network withoutwasting previously-deployed wireless sensor network elements orrequiring significant time or expense in modifying thepreviously-deployed wireless sensor network.

FIG. 1 illustrates an example embodiment of a wireless sensor networkthat can collect and distribute sensor information. The wireless sensornetwork can be configured to collect and distribute sensor informationthat is based on measurements by sensors deployed at monitored location110. Monitored location 110 can represent any area where a collection ofsensors is deployed. Monitored location 110 may or may not represent aphysical area having clearly defined boundaries. As would beappreciated, the extent of the monitoring application itself provides asense of boundary to monitored location 110. In one example, monitoredlocation 110 can represent a building such as a home, hotel, school,community building, stadium, convention center, warehouse, officebuilding, multi-dwelling unit, or other defined building structure. Inanother example, monitored location 110 can represent an area of controlsuch as a monitored area that can be fixed or movable.

Disposed within monitored location 110 is a plurality of sensors.Communication between the plurality of sensors and gateway device 120 isfacilitated by a set of wireless nodes 130-n. In general, wireless nodes130-n can be configured to form a wireless mesh network. In oneembodiment, the communication protocol between wireless nodes 130-n isbased on the IEEE 802.15.4 protocol. A wireless mesh network can beformed between wireless nodes 130-n and can be used to facilitatecommunication between any wireless node 130-n and gateway device 120.

A wireless node 130-n can be configured to support one or more sensormodule units (S), each of which can be individually coupled to awireless node 130-n via a plug-and-play universal sensor interface. Theplug-and-play universal sensor interface facilitates the separation ofthe wireless node communication infrastructure from the set of one ormore sensor module units that are deployed at the location at which thesupporting wireless node 130-n is installed. This separation createssignificant flexibility in choice of sensors that may or may not bedeployed proximate to the time of installation of the supportingwireless node 130-n. As such, the plug-and-play universal sensorinterface enables a sensor network solution to respond to changes in thesensor application requirements at monitored location 110 withoutincurring significant re-deployment costs.

This flexibility would not be available if sensors were integrated witha wireless node. When a wireless node is deployed with integratedsensors, the monitoring capability of the wireless node is limited tothe sensors that were pre-installed in the wireless node. Thispre-installation would fix the capability of the wireless node at thetime of deployment and would limit the wireless node to a static sensorapplication objective. Thus, if a defective sensor needs to be replaced,or if another type of sensor needs to be added to meet a dynamic sensorapplication objective, then the wireless node would need to be replacedor otherwise modified. This would impact at least part of the wirelesssensor network infrastructure, which can result in sensor networkdowntime at the monitored location. A further impact would be producedas the maintenance expense of such a replacement or modification wouldbe prohibitive.

In the present disclosure, the plug-and-play universal sensor interfaceenables the sensor module units to be deployed separately from wirelessnodes 130-n. The plug-and-play universal sensor interface allows anytype of sensor module unit to be connected to any wireless node 130-n atany time and without any reconfiguration of the supporting wirelessnetwork infrastructure. This feature allows great flexibility in thedeployment and modification of wireless sensor networks at a lower pricepoint. Additionally, the plug-and-play universal sensor interfaceenables the monitoring capabilities of the wireless sensor network toscale seamlessly with the dynamic nature of changing sensor applicationobjectives.

In one example, a wireless node 130-n can be configured to support foursensor module units. As would be appreciated, the particular number ofsensor module units that can be supported by a wireless node 130-n canvary. Sensor module units can be added onto wireless nodes 130-nsequentially at different deployment times. Thus, for example, a firstsensor module unit can be added at a time of installation of thewireless node 130-n, with one or more additional sensor module unitsadded to the same wireless node 130-n in the future as needed to addresschanging sensor application objectives.

In one embodiment, each of the sensor module units can support aplurality of individual sensors. In one example, a sensor module unitcan support a set of eight sensors. In this example, the set of eightsensors can include sensors of one or more types. For example, sensorsin a sensor module unit can include one or more of the following: atemperature sensor, a humidity sensor, an air quality sensor (e.g., CO₂sensor), a light sensor, a sound sensor, a contact sensor, a pulsesensor, a water sensor, or any other type of sensor configured tomeasure a characteristic of a part of monitored location 110. A sensormodule unit can include multiple sensors of a single type. For example,a particular configuration of a sensor module unit can include fourpulse sensors, one temperature sensor, one humidity sensor, one airquality sensor, and one light sensor. In another example, a particularconfiguration of a sensor module unit can include eight sensors of asingle type. As would be appreciated, the set of sensors included withina particular sensor module unit can be chosen to meet a given sensorapplication objective.

In the present disclosure, it is recognized that sensor module units canbe targeted or otherwise designed for a particular class of sensorapplications. For example, one sensor module unit can be designed forsensor applications targeted to school buildings, while another sensormodule unit can be designed for sensor applications targeted to officebuildings. The sensor module unit targeted for school building use caninclude a set of sensors that are popular with school building sensorapplications. For instance, the set of sensors can include pulse sensorsfor measuring utility consumption (e.g., gas, water, electricity), atemperature sensor, an air quality sensor, a humidity sensor and a lightsensor. The sensor module unit targeted for school building use can thenbe selected for installation with wireless nodes deployed in schoolbuildings. In this manner, a relatively generic sensor module unit canbe deployed across many sensor application deployments in variousschools without requiring full customization for a specific applicationat a particular school. Production costs of the sensor module units arethereby minimized without any loss of flexibility in deployingcustomized sensor module units.

The impact on economies of scale can be readily appreciated. Wirelessnode modules can be produced on a larger manufacturing scale because thegeneric wireless nodes can be applied in many types of monitoredlocations in a manner that is separate from the particular sensorobjectives at the particular monitored location. Correspondingly, alimited number of types of sensor module units can be manufactured. Forexample, a first sensor module unit type can be produced for officebuilding applications and can include a suite of sensors typically usedin office buildings. Similarly, a second sensor module unit type can beproduced for school building applications and can include a suite ofsensors typically used in school buildings.

In the deployment at a particular monitored location, the genericwireless nodes can be installed at the particular monitoring points inthe monitored location with the particular type of sensor module unitattached to the generic wireless node to meet the particular needs atthat monitoring point. Customization of this nature is far superior tothe limited options presented by integrated devices. Customization neednot result in wireless sensor network downtime and can be effectedthrough the selective coupling of particular sensor module units towireless nodes.

In the deployment at a particular monitored location, the genericwireless nodes can be installed at the particular monitoring points inthe monitored location with the particular type of sensor module unitattached to the generic wireless node to meet the particular needs atthat monitoring point. Customization of this nature is far superior tothe limited options presented by integrated devices. Customization neednot result in wireless sensor network downtime and can be effectedthrough the selective coupling of particular sensor module units towireless nodes.

A further benefit of this form of customization is that it obviates theneed to re-qualify and test wireless nodes to meet a new sensorapplication. Qualification need only be performed on new sensor moduleunits since the existing wireless network infrastructure provided by thegeneric wireless nodes had previously been qualified and tested. Thisreduces the time needed to bring new sensor network features to marketin addressing new market opportunities. If, on the other hand, sensorswere integrated with the wireless nodes, then the entire device wouldneed to be re-qualified and tested before being brought to market. Asdescribed, the plug-and-play universal sensor interface enables sensornetwork application customization without increasing installation andmaintenance costs of the sensor network infrastructure.

Returning to FIG. 1, wireless node 130-1 is illustrated as supporting asingle sensor module unit (S). Wireless node 130-2, on the other hand,is illustrated as not supporting any sensor module units. This exampleillustrates a scenario where wireless node 130-2 has been specificallyinstalled as a wireless relay node in a wireless mesh network tofacilitate a connection between wireless node 130-1 and gateway 120. Asfurther illustrated, wireless node 130-3 supports four different sensormodule units (S). This example illustrates a scenario where the sensingneeds of a particular part of monitored location 110 is greater andwould therefore require additional installed sensors at the location ofwireless node 130-3. For instance, wireless node 130-3 can be installedin a hub of sensing activity at monitored location 110, while wirelessnode 130-1 or wireless node 130-N can be installed in a periphery ofsensing activity at monitored location 110. The plug-and-play universalsensor interface enables sensor module unit deployment to match sensorapplication needs in a manner that scales seamlessly with the deployedwireless network infrastructure. Deployment and maintenance costs arethereby contained.

The wireless mesh network created by wireless nodes 130-n facilitatescommunication between sensor module units and gateway 120 via thewireless network infrastructure established by wireless nodes 130-n.Gateway 120 can be installed at monitored location 110 and can beprovided with network connectivity. For example, gateway 120 can beprovided with a network connection that facilitates communication ofsensor data to host system 140. The network connection can be embodiedin various forms depending upon the particular characteristics ofmonitored location 110.

For example, where monitored location 110 is a building in a developedarea, then the network connection can be facilitated by a wired Internetconnection via an Internet service provider. In another example, wheremonitored location 110 represents a remote physical area (or movablearea) that may or may not include a building structure, then the networkconnection can be facilitated by a terrestrial or satellite basedwireless network. As would be appreciated, the principles of the presentdisclosure would not be dependent on the particular form of networkconnection supported by gateway 120 in communicating with host system140.

The network connection between gateway 120 and host system 140 enablesthe collection of sensor data by host system 140. In one embodiment,host system 140 can be located in a location remote from gateway 120. Ingeneral, host system 140 can be configured to perform a collection ofsensor data from monitored location 110, storage of sensor data indatabase 142, and a distribution of sensor data to one or moredestinations. As illustrated, host system 140 can include one or moreservers 141 that can facilitate the collection, storage and distributionprocesses.

As described, wireless nodes 130-n provide a wireless networkinfrastructure upon which sensor module units can be deployed for acustomized sensor application. FIG. 2 illustrates an example embodimentof a wireless node. As illustrated, wireless node 200 includescontroller 210 and wireless transceiver 220. In one embodiment, wirelessnode 200 can be powered via a battery source (not shown). In anotherembodiment, wireless node 200 can be powered via an external powersource available at the point of installation at the monitored location.

Wireless transceiver 220 facilitates wireless communication betweenwireless node 200 and a gateway or another wireless node that operatesas a relay between wireless node 200 and the gateway. The sensor datacommunicated by wireless transceiver 220 is collected by controller 210via one or more universal sensor interfaces 230-n. Each universal sensorinterface 230-n can support connection of wireless node 200 with aseparate sensor module unit that can be attached to wireless node 200.

Universal sensor interfaces 230-n can represent a combination ofhardware and software. The hardware portion of universal sensorinterfaces 230-n can include a wired interface that enablescommunication of different signals between wireless node 200 and aconnected sensor module unit. In one example, the wired interface can beenabled through a connector interface, which is exposed by the housingof the wireless node 200, and that is configured to receive a sensormodule unit connector via removable, pluggable insertion.

In one embodiment, the wired interface can be based on a SerialPeripheral Interface (SPI) bus. In one example, the wired interfaceenables six connections: supply, ground, data in, data out, clock, anddevice select. The device select connection can be unique to each wiredinterface and can enable controller 210 in wireless node 200 to selectthe particular sensor module unit with which wireless node 200 desiresto communicate. The software portion of the universal sensor interfaces230-n can include a protocol that allows wireless node 200 tocommunicate with a sensor module unit.

In one example protocol, controller 210 can be configured to poll thevarious universal sensor interfaces 230-n to determine whether anysensor module units are connected. As part of this protocol, controller210 can first request a sensor ID from a sensor module unit. If theresponse read is 0, then controller 210 would know that no sensor moduleunit is connected to that universal sensor interface 230-n. If, on theother hand, the response read is not 0, then controller 210 would askfor the number of data values that have to be retrieved and the numberof bits on which the data values are coded. In one example, the higherorder 8-bits of a 16-bit communication between controller 210 and asensor module unit identifies the number of data values, while the lowerorder 8-bits of the 16-bit communication identifies the number of bitsused to code each data value. Based on the number of data values to beretrieved, controller 210 would then collect that number of data values,wherein each value can represent a different sensor channel of thesensor module unit.

In one example, a wireless node can be configured for coupling to fourdifferent sensor module units. If each of the sensor module units caninclude up to eight sensors, then the wireless node can be configured tocommunicate 32 sensor channels of data to the gateway via wirelesstransceiver 220.

In the illustration of FIG. 2, wireless node 200 also includes one ormore sensors 240-n. In one example, sensors 240-n can be containedwithin or otherwise supported by the housing of wireless node 200. Invarious scenarios, the one or more sensors 240-n can facilitatemonitoring at that part of the monitored location, including the healthand/or status of wireless node 200. In one example configuration,sensors 240-n can include a temperature sensor, a humidity sensor, avoltage sensor, a link quality sensor, or any other sensor that can beused to facilitate the sensing needs of wireless node 200.

As noted, wireless nodes can be designed as a generic communication nodeupon which customized sensing functionality can be added through theconnection of particular sensor module units. In this framework, thewireless nodes can be constructed with base communication functionalitythat can operate independently of particular sensors. As such, thewireless nodes can provide a relatively stable wireless networkinfrastructure that can support multiple generations of sensor moduleunits. As would be appreciated, the requirements of the sensor moduleunits would be dependent on the particular sensing application. Forexample, a first sensor module unit can be designed with a firstgeneration sensor having a first degree of accuracy, reliability, orother sensor characteristic, while a second sensor module unit can bedesigned with a second generation sensor of the same type having asecond degree of accuracy, reliability, or other sensor characteristic.As this example illustrates, different generations of sensor moduleunits can be attached to the same wireless node using the plug-and-playuniversal sensor interface. The original investment in the wireless nodewould not be lost should the second sensor module unit replace theoriginally-installed first sensor module unit. A low-cost evolutionarypath of the wireless sensor network would therefore be enabled thatcould scale seamlessly with a customer's needs, sensor technology, orother factor that implicates a sensor module unit modification.

FIG. 3 illustrates an example embodiment of a sensor module unitdesigned for attachment to a wireless node. As illustrated, sensormodule unit 300 includes controller 310 that communicates over auniversal sensor interface with the wireless node. In one embodiment,sensor module unit 300 supports a connector 320 configured forpluggable, removable insertion into a connector interface exposed by thewireless node. In another embodiment, the sensor module unit can becoupled to the connector interface exposed by the wireless node via aconnector attached to a cable.

Sensor module unit 300 can include a plurality of sensors 330-n. In oneexample, sensor module unit 300 includes up to eight sensors of one ormore types. In the present disclosure, it is recognized that a sensormodule unit can be pre-populated with a suite of sensors targeted to aparticular class of sensor applications. In this framework, a firstsuite of sensors can be used in a first sensor module unit targeted to afirst sensor application (e.g., school buildings), while a second suiteof sensors can be used in a second senor module unit targeted to asecond sensor application (e.g., office buildings) different from thefirst sensor application. Here, the underlying wireless networkinfrastructure can remain the same while particular sensor module unitsare chosen for coupling to one or more wireless nodes to facilitate aparticular sensor application at a monitored location.

The plug-and-play nature of the connection of sensor module units tosupporting wireless nodes facilitates a modular framework ofinstallation of a wireless sensor network. FIG. 4 illustrates an exampleembodiment of a housing of a wireless node that exposes a plurality ofconnector interfaces to produce the modular framework. As illustrated,wireless node 400 can have a housing configured to expose a plurality ofconnector interfaces 410. Each of the plurality of connector interfaces410 can support the physical attachment of a single sensor module unit.In the example illustration, each side of the housing of wireless node400 exposes a single connector interface 410. In the present disclosure,it is recognized that the housing of the wireless node can besubstantially larger than the housing of the sensor module unit. Thiscan result, for example, because the wireless node can be designed withadditional components such as an internal power source (e.g., battery)that can involve additional volume requirements as compared to thesensor module units. It is therefore recognized that one embodiment of awireless node can have multiple sensor module units physically attachedto a single side of the wireless node.

FIG. 5 illustrates an example embodiment of a housing of a sensor moduleunit that enables the modular framework. As illustrated, sensor moduleunit 500 supports a connector 510 that can be configured for pluggable,removable insertion into a corresponding connector interface 410 exposedby the housing of wireless node 400. The connection of sensor moduleunit 500 to wireless node 400 via the insertion of connector 510 intoconnector interface 410 produces a true plug-and-play framework ofwireless sensor network deployment.

FIG. 6 illustrates an example embodiment of a wireless node that isphysically attached to a plurality of sensor module units via universalsensor interfaces. As illustrated, wireless node 600 is attached tosensor module unit 620-1, sensor module unit 620-2, sensor module unit620-3, and sensor module unit 620-4 via four connector interfacesexposed by the housing of wireless node 600. The attachment of sensormodule unit 620-1 to wireless node 600 enables communication of sensordata between controller 621-1 and controller 610. The attachment ofsensor module unit 620-2 to wireless node 600 enables communication ofsensor data between controller 621-2 and controller 610. The attachmentof sensor module unit 620-3 to wireless node 600 enables communicationof sensor data between controller 621-3 and controller 610. Finally, theattachment of sensor module unit 620-4 to wireless node 600 enablescommunication of sensor data between controller 621-4 and controller610. Each of sensor module units 620-1 to 620-4 can be coupled towireless node 600 via a separate universal sensor interface having theconnectivity characteristics described above.

Controller 610 in wireless node 600 can communicate with each of sensormodule units 620-1 to 620-4 to retrieve sensor data generated by one ormore sensors on the respective sensor module units 620-1 to 620-4. Inone embodiment, the sensor channels of data that are communicated fromsensor module unit 620-n to wireless node 600 are configurable. Asnoted, communication between controller 610 and the sensor module units620-1 to 620-4 can be based on a protocol that enables identification ofthe number of data values that are transmitted from each of sensormodule units 620-1 to 620-4 to controller 610.

In one embodiment, a sensor module unit can be configured to transmitdata from only a subset of the sensors on the sensor module unit. Toillustrate this embodiment, consider again the example of a sensormodule unit targeted for school building use. In this example, thesensor module unit can include a standard suite of eight sensors,including four pulse sensors for measuring utility consumption (e.g.,gas, water, electricity), a temperature sensor, an air quality sensor, ahumidity sensor and a light sensor. Individual sensors in this standardsuite of sensors can be activated selectively such that only a subset ofthe sensor channels of data is forwarded from the sensor module unit tothe wireless node.

Here, it is recognized that the selective transmission of sensorchannels of data can be used to support efficient wireless bandwidth useor reduced power consumption within the wireless sensor network at themonitored location. Moreover, the selective transmission of sensorchannels of data can support a billing model where customers pay persensor channel stream of data that is exposed by the host system to thecustomer. Additionally, customization of a sensor module unit afterinstallation enables remote customization, which thereby lowers the costof installation and maintenance incurred by personnel responsible forconfiguring the wireless sensor network at the monitored location. Aswould be appreciated, this aspect of configuration can be designed toreduce the amount of pre-installation customization required in settingup sensor module unit 620-n to operate with wireless node 600 at themonitored location.

FIG. 7 illustrates an example embodiment of the configuration of a setof sensor channels between a sensor module unit and a wireless node. Asillustrated, wireless node 700 includes controller 710, while sensormodule unit 720 includes controller 721. Controller 710 in wireless node700 and controller 721 in sensor module unit 720 are configured tocommunicate using a universal sensor interface such as that describedabove.

In this example, assume that sensor module unit 720 includes eightsensors 722-1 to 722-8 (e.g., four pulse sensors for measuring utilityconsumption, one temperature sensor, one air quality sensor, onehumidity sensor and one light sensor), which can represent a standardsuite of sensors targeted for school building use. After sensor moduleunit 720 has been attached to wireless node 700 via a universal sensorinterface, channels of data associated with a first subset of the suiteof eight sensors 722-1 to 722-8 can be activated, while channels of dataassociated with a second subset of the suite of eight sensors 722-1 to722-8 can be deactivated.

For example, assume that sensors 722-1 to 722-4 are pulse sensors,sensor 722-5 is a temperature sensor, sensor 722-6 is an air qualitysensor, sensor 722-7 is a humidity sensor, and sensor 722-8 is a lightsensor. As illustrated, sensor module unit 720 can be configured suchthat channels of data associated with a first subset of sensors,including pulse sensor 722-1, temperature sensor 722-5 and humiditysensor 722-7 are activated. Correspondingly, sensor module unit 720 canbe configured such that channels of data associated with a second subsetof sensors, including pulse sensors 722-2 to 722-4, air quality sensor722-6 and light sensor 722-8 are deactivated. This example can representa scenario where the part of the monitored location at which wirelessnode 700 is installed has only one measurable utility consumption (e.g.,water) that requires monitoring along with a need for temperature andhumidity sensor readings.

Since channels of data associated with pulse sensors 722-2 to 722-4, airquality sensor 722-6 and light sensor 722-8 have been deactivated,controller 721 would report to controller 710 that controller 721 hasonly three data values for retrieval. These three data values arerepresented by the sensor channels 730-1, 730-4 and 730-7 that arepassed between controller 721 in sensor module unit 720 to controller710 in wireless node 700 over the universal sensor interface. As thisexample illustrates, the configuration of the activated/deactivatedsensor channels of data enables customization to meet the particularneeds of a particular part of a monitored location.

As noted, the wireless node can be coupled to a plurality of sensormodule units. Different subsets of sensor channels of data in eachsensor module unit can be activated/deactivated as needed. Incombination, a customized set of sensor channels of data across theplurality of sensor module units can be activated/deactivated as needed.

Here, it should be noted that the relative activation of sensor channelsof data in the wireless sensor network can be accomplished in a varietyof ways. FIG. 8 illustrates a framework of the relative activation ofsensor channels of data in the wireless sensor network. In thisillustration, wireless sensor node unit 800 can represent a combinationof a sensor module unit and a wireless node. In a manner similar to FIG.7, example wireless sensor node unit 800 is illustrated as containingeight sensors 822-1 to 822-8. In a configured mode of operation ofwireless sensor node unit 800, channels of data associated with a firstsubset of sensors is activated and channels of data associated with asecond subset of sensors is deactivated or managed in a manner differentfrom the channels of data associated with the first subset of sensors.The first subset of sensors, which includes sensor 822-1, sensor 822-5and sensor 822-7, produces activated sensor data 821. Activated sensordata 821 is transmitted to a gateway device via a wireless transceiver.

The selective transmission of activated sensor data 821 to a gatewaydevice is characteristic of the configured mode of operation of wirelesssensor node unit 800. The configured mode of operation can be effectedin a number of different ways.

In one embodiment, the configured mode of operation can be effected suchthat the second subset of sensors do not perform any sensormeasurements. In this embodiment, one or more components associated withthe second subset of sensors can enter an unpowered or other energysaving state such that power consumption is minimized. In general,maximizing power savings by powering down any unneeded component wouldmaximize the lifetime of internal powering solutions (e.g., batterypower). This extended lifetime would lower the maintenance costs of thewireless sensor network in delaying action by a service technician(e.g., replacing an internal battery).

In another embodiment, the configured mode of operation can be effectedsuch that a controller in the sensor module unit is prevented fromcollecting or otherwise retrieving data from the second subset ofsensors. In one example, the one or more of the second subset of sensorscan remain powered, but the controller in the sensor module unit doesnot collect or otherwise retrieve data from the second subset ofsensors. In one scenario, the interface between the controller and asensor in the second subset of sensors can be deactivated. FIG. 7provides an illustration of this scenario, where the interfaces betweencontroller 721 and sensor 722-2, sensor 722-3, sensor 722-4, sensor722-6 and sensor 722-8 are deactivated.

In another embodiment, the configured mode of operation can be effectedsuch that a controller in the sensor module unit has obtained sensordata from the second subset of sensors, but does not forward theobtained sensor data to the wireless node via the wired interface. Inone example, the second subset of sensors can continue to take sensormeasurements and forward those sensor measurements to the controller inthe sensor module unit. The controller can then be configured to forwardonly the sensor measurements from the first subset of activated sensorsto the wireless node.

In yet another embodiment, the configured mode of operation can beeffected such that the controller in the wireless node has obtainedsensor data from the second subset of sensors, but does not forward theobtained sensor data to the gateway via the wireless transceiver. In oneexample, the sensor module unit can continue to take sensor measurementsand forward those sensor measurements to the controller in the wirelessnode. The controller can then be configured to forward only the sensormeasurements from the first subset of activated sensors to the gateway.This embodiment is useful where wireless bandwidth in the wirelesssensor network is of concern. Effectively, the controller in thewireless node can be configured to filter the sensor channels that aretransmitted to the gateway.

As has been illustrated, the configured mode of operation of thewireless sensor node unit can limit the transmission of sensor data tothe gateway in a variety of ways. In various examples, the limitationeffected by the configured mode of operation can influence the operationof the sensors, the operation of the interface between the sensor andthe controller in the sensor module unit, the operation of thecontroller in the sensor module unit, the operation of the universalsensor interface, the operation of the controller in the wireless node,the operation of the wireless transceiver, or the operation of any othercomponent in the sensor data path. The particular mechanism used by theconfigured mode of operation would be implementation dependent. Ingeneral, the configured mode of operation can be designed to limit thecollection and/or forwarding of data in the data path originating at thesecond subset of sensors.

A configured mode of operation can be established based on configurationsetup information that is made available to the wireless node from thehost system. In one example, the configuration setup information isbased on a configuration command generated by a configuration station(e.g., personal computer, tablet, mobile phone, or other computingdevice), which can be enabled to identify a particular configured modeof operation for the sensor module unit and/or the wireless node.

FIG. 9 illustrates a framework for enabling remote configuration of theoperation of the wireless sensor network at the monitored location. Asillustrated, host system 940 can support configuration station 950. Inone embodiment, host system 940 provides configuration station 950 withcomputer readable program code that enables configuration station 950 torender a user interface (e.g., web interface). The user interfaceenables a user at configuration station 950 to identify a configuredmode of operation for the operation of the wireless sensor network.Through the interaction by a user with the user interface presented atconfiguration station 940, configuration station 950 can generate aconfiguration command that is transmitted to host system 940. Ingeneral, the configuration command can be designed to produce one ormore actions that influence or otherwise modify the operation of thewireless sensor network.

In the illustrated example, the configuration command is received byhost system 940 and used as the basis for generating configuration setupinformation that is subsequently transmitted to one or more wirelessnodes such as wireless node 930-X. In the general sense, configurationsetup information can be used to influence or otherwise modify theoperation of any element in a data path between host system 940 and asensor module unit attached to a wireless node. For example, thegenerated configuration setup information can be used to influence orotherwise modify the operation of a component within host system 940,gateway 920, wireless node 930-X, and/or a sensor module unit attachedto wireless node 930-X.

By this process, configuration station 950 can be used to effect remoteconfiguration of the wireless sensor network. It is a feature of thepresent disclosure that the remote configuration provides furtherflexibility in enabling post-installment configuration. Features andcapabilities of the wireless sensor network would therefore not beconstrained to pre-installed features. Rather, features in the wirelesssensor network can be dynamically added or modified after theinstallation of a base of modular components. Installation andconfiguration costs of the wireless sensor network are thereforeminimized.

FIG. 10 illustrates an example embodiment of the use of remoteconfiguration for activation of sensor channels of data. As illustrated,configuration station 1050 supports the provision of a user interface1051 that enables a user to activate/deactivate particular sensorchannels of data at monitored location 1010. In one example, a settingsmodule supported by host system 1040 can transmit computer readableprogram code (communication 1) from a server device to configurationstation 1050 that enables configuration station 1050 to render userinterface 1051 (e.g., web interface). Through the interaction by theuser with user interface 1051 on configuration station 1050, the usercan specify the details of particular sensor channels of data thatshould be activated/deactivated. As noted, this activation/deactivationof sensor channels of data would effect a change in the collectionand/or reporting of sensor channels of data by a sensor module unit, awireless node, a gateway, and/or a host system.

User interface 1051 enables a user to specify a particular wirelessnode. In various embodiments, the wireless node can be specified using awireless node ID, a pseudo-name for the wireless node, or any othermechanism that enables individual identification of a wireless node. Thespecification of a particular wireless node can also be facilitated by agrouping of deployed wireless nodes per monitored location. In theillustrated example of FIG. 10, the identification of “Wireless Node X”would correspond to wireless node 1030-X at monitored location 1010.

After identification of wireless node 1030-X, user interface 1051 wouldthen enable the user to identify a particular port of wireless node1030-X. For example, where wireless node 1030-X includes four ports thateach expose an interface connector for physical attachment to aconnector on a sensor module unit, user interface 1051 would enableselection of any of the four ports. In the illustrated example of FIG.10, the identification of “Port Y” would correspond to the sensor moduleunit attached to port Y of wireless node 1030-X at monitored location1010.

Next, user interface 1051 would enable the user to specify, for eachincluded sensor in the sensor module unit attached to port Y of wirelessnode 1030-X, whether that sensor channel of data is activated ordeactivated. In the illustrated example of FIG. 10, the user hasactivated the channel of data associated with Sensor 1, deactivated thechannel of data associated with Sensor 2, activated the channel of dataassociated with Sensor 3, . . . , and deactivated the channel of dataassociated with Sensor N.

Through the interaction by a user with user interface 1051, anactivation/deactivation status of each sensor channel of data in thesensor module unit attached to port Y of wireless node 1030-X would bespecified. The specification of the activation/deactivation status ofeach sensor channel of data can then be returned as a configurationcommand (communication 2) to host system 1040. In one embodiment, hostsystem 1040 can store an activation/deactivation status for each sensorchannel of data in a database based on the received configurationcommand. In one example, the activation/deactivation status for a sensorchannel of data is stored in accordance with an identifier based on agateway identifier, a wireless node identifier, a port identifier and asensor identifier.

Based on the remotely-configured activation/deactivation status, hostsystem 1040 can then generate configuration setup information for theconfiguration of the sensor channels of data in the sensor module unitattached to port Y of wireless node 1030-X at monitored location 1010.In one embodiment, host system 1040 would transmit the generatedconfiguration setup information (communication 3) to wireless node1030-X via gateway 1020. The configuration setup information can then beused by wireless node 1030-X in configuring the operation of the sensormodule unit attached to port Y and/or the operation of wireless node1030-X. After configuration, wireless node 1030-X would transmitactivated sensor channels of data (communication 4) back to host system1040 for subsequent distribution.

As noted above, the activation/deactivation of individual sensorchannels of data can effectively be performed at different parts of thesensor module unit and/or wireless node. The particular mechanism bywhich the configuration setup information would be used would thereforebe implementation dependent. For example, the configuration setupinformation can be used to influence the operation of the sensors, theoperation of the interface between the sensor and the controller in thesensor module unit, the operation of the controller in the sensor moduleunit, the operation of the universal sensor interface, the operation ofthe controller in the wireless node, the operation of the wirelesstransceiver, or the operation of any other component in the sensor datapath.

In one embodiment, the configuration setup information would not producea change in the transmissions by wireless node 1030-X, which can forwardsensor channels of data from all sensors. In this example, theconfiguration setup information can be used by gateway 1030 and/or hostsystem 1040 to influence the operation of gateway 1030 and/or hostsystem 1040 in forwarding only a select set of sensor channels of datathat have been activated. This selective transmission of sensor channelsof data can support a billing model where customers pay per sensorchannel stream of data that is exposed by the host system to thecustomer.

As has been described, user interface 1051 on configuration station 1050enables a user to remotely configure an activation/deactivation statusfor every sensor channel of data associated with every sensor in everysensor module unit attached to every wireless node at the monitoredlocation. Here, the activation/deactivation status specified atconfiguration station 1050 produces a change in the collection and/orprocessing of sensor channels of data that are performed by one or moreof a sensor module unit, a wireless node, a gateway, and a host system.This change in the collection and/or processing of sensor channels ofdata at units remote from configuration station 1050 enables a scalablewireless sensor network solution that reduces installation andmaintenance costs as the wireless sensor network evolves to addresschanging sensor application needs at a particular monitored location.

The example embodiment illustrated in FIG. 10 represents one exampleapplication of the remote configuration framework presented in FIG. 9.Additional applications of the remote configuration framework are nowdescribed.

FIG. 11 illustrates an example embodiment of a remote configuration of areporting interval at a monitored location. As illustrated,configuration station 1150 supports the provision of user interface 1151that enables a user to specify data reporting intervals for individualsensor module units installed at monitored location 1110. In oneexample, a settings module supported by host system 1140 can transmitcomputer readable program code (communication 1) from a server device toconfiguration station 1150 that enables configuration station 1150 torender user interface 1151. Through the interaction by the user withuser interface 1151 on configuration station 1150, the user can specifythe data reporting frequency for particular sensor module units, whicheffects a change in the type of processing performed by sensor moduleunits, wireless nodes and/or a gateway device.

User interface 1151 enables a user to specify a particular wireless nodein a manner similar to that described with reference to FIG. 10. In theillustrated example of FIG. 11, the identification of “Wireless Node X”would correspond to wireless node 1130-X in monitored location 1110.

After identification of wireless node 1130-X, user interface 1151 wouldthen enable the user to identify a particular port of wireless node1130-X. For example, where wireless node 1130-X includes four ports thateach expose an interface connector for physical attachment to aconnector on a sensor module unit, user interface 1151 would enableselection of any one of the four ports. In the illustrated example ofFIG. 11, the identification of “Port Y” would correspond to the sensormodule unit attached to port Y of wireless node 1130-X at monitoredlocation 1110.

Next, user interface 1151 would enable the user to specify, for thesensor module unit attached to port Y of wireless node 1030-X, a definedsensor data reporting interval. For example, the user can be givendifferent options regarding a sensor data reporting interval such asevery 10 minutes, every 15 minutes, every 30 minutes, or any otherdefined time period interval. In the illustrated example of FIG. 11, theuser has selected Reporting Interval B.

Through the interaction by a user with user interface 1151, a datareporting interval for the sensor module unit attached to port Y ofwireless node 1130-X in monitored location 1110 would be specified. Thespecification of the data reporting interval for the sensor module unitcan then be returned as a configuration command (communication 2) tohost system 1140. In one embodiment, a specified data reporting intervalfor each sensor module unit can be stored in a database based on thereceived configuration command. In one example, the specified datareporting interval is stored in accordance with an identifier based on agateway identifier, a wireless node identifier, and a port identifier.

Based on the remotely-configured data reporting interval, host system1140 can then generate configuration setup information for theconfiguration of the wireless nodes in monitored location 1110. In oneembodiment, host system 1140 would transmit the generated configurationsetup information (communication 3) to wireless node 1130-X via gateway1120. The configuration setup information can then be used by wirelessnode 1130-X in configuring the reporting of sensor data from the sensormodule unit attached to port Y of wireless node 1130-X. Afterconfiguration, wireless node 1130-X would perform periodic sensor datareports from the sensor module unit attached to port Y of wireless node1130-X in accordance with the specified reporting interval.

Here, it should be noted that the data collection reporting applied on aper sensor module unit basis is for illustration purposes only. Moregenerally, the data reporting interval can be specified at whateverlevel of granularity is required for the needs of monitored location1110. In one embodiment, a user can specify that the same data reportinginterval be applied to all wireless nodes at monitored location 1110. Inanother embodiment, a user can specify separate data reporting intervalsfor each wireless node, wherein all sensor module units for a particularwireless node would share the same data reporting interval. In anotherembodiment, the data reporting interval can be performed on a per sensorchannel of data basis such that a first sensor in a sensor module unitwould report sensor data to a wireless node at a different frequencythan a second sensor in that same sensor module unit. In this example,the specified data reporting interval is stored in accordance with anidentifier based on a gateway identifier, a wireless node identifier, aport identifier and a sensor identifier.

The different granularity of control provided with respect to the datareporting interval is designed to address differences in monitoringacross monitored location 1110. There may exist, for example, certainparts of monitored location 1110 that are more or less critical thanothers, certain sets of sensors that are more or less critical thanothers, and/or certain individual sensors that are more or less criticalthan others. Through the use of configuration station 1150, a user canspecify data reporting intervals that are customized for differentsensors, different sensor module units, different wireless nodes, and/orother groupings of wireless sensor network elements that share areporting interval characterization.

Regardless of the particular level of granularity used to specify one ormore data reporting intervals through user interface 1151, the generatedconfiguration command(s) would form the basis of configuration setupinformation that is transmitted from host system 1140 to gateway 1120.Depending on the granularity of the control effected using userinterface 1151, gateway 1120 can transmit configuration setupinformation that is applicable to all or part of the wireless sensornetwork. In one example, the receipt of the configuration setupinformation by wireless node 1130-X would cause wireless node 1130-X toconfigure the intervals at which it would communicate with all or partof the connected sensor module units to enable sensor data reports forone or more sensors.

As has been described, user interface 1151 on configuration station 1150enables a user to remotely configure a data reporting interval for everysensor channel of data produced by every sensor in every sensor moduleunit attached to every wireless node at the monitored location. Here,the data reporting interval specified at configuration station 1150produces a change in the collection and/or processing of sensor channelsof data at remote units such as a sensor module unit and a wirelessnode. This change in the collection and/or processing of sensor channelsof data at units remote from configuration station 1150 enables ascalable wireless sensor network solution that reduces installation andmaintenance costs as the wireless sensor network evolves to addresschanging sensor application needs at a particular monitored location.

FIG. 12 illustrates an example embodiment of a remote configuration of atransformation function for a sensor channel of data. As illustrated,configuration station 1250 supports the provision of user interface 1251that enables a user to specify a transformation function for aparticular sensor channel of data. In one example, a settings modulesupported by host system 1240 can transmit computer readable programcode (communication 1) from a server device to a client device thatenables configuration station 1250 to render user interface 1251.Through the interaction by the user with user interface 1251 onconfiguration station 1250, the user can specify the details of aparticular transformation function to be applied to a particular sensorchannel of data, which effects a change in the type of processingperformed by host system 1240.

User interface 1251 enables a user to specify a particular wireless nodein a manner similar to that described with reference to FIG. 10. In theillustrated example of FIG. 12, the identification of “Wireless Node X”would correspond to wireless node 1230-X in monitored location 1210.

After identification of wireless node 1230-X, user interface 1251 wouldthen enable the user to identify a particular port of wireless node1230-X. For example, where wireless node 930-X includes four ports thateach expose a connector interface for physical attachment to a connectoron a sensor module unit, user interface 951 would enable selection ofany one of the four ports. In the illustrated example of FIG. 12, theidentification of “Port Y” would correspond to the sensor module unitattached to port Y of wireless node 1230-X at monitored location 1210.

Next, user interface 1251 would enable the user to activate atransformation function for the sensor channel of data corresponding toa particular sensor in the sensor module unit attached to port Y ofwireless node 1230-X at monitored location 1210. In the illustratedexample of FIG. 12, the user has activated the transformation functionfor sensor “n” in the sensor module unit attached to Port Y. As part ofthis process, user interface 1251 can also enable the user to specify aparticular transformation function for the sensor channel correspondingto sensor “n.” In one embodiment, user interface 1251 can provide apre-defined listing of transformation functions that can be applied tothe sensor channel of data. In the illustrated example, the user hasactivated Transformation Function A for the sensor channel of datacorresponding to sensor “n.” As would be appreciated, varioususer-interface mechanisms can be used to enable a user to customize atransformation function for the selected sensor channel of data.

To illustrate the value of a specified transformation function, considerthe example of a pulse sensor in FIG. 13. As illustrated, pulse sensor1310 can be coupled to utility meter 1320 via a pair of conductors. Theactual wired interface between pulse sensor 1310 and utility meter 1320can vary depending on the type of utility meter that is present. Asillustrated, pulse sensor 1310 can be configured to provide 3.3V on afirst conductor. Utility meter 1320 includes a dry contact relay thatwould successively relay the 3.3V provided by pulse sensor 1310 and thenopen the relay. In one example, a first state of the relay cancorrespond to a first part of a disk rotation, while a second state ofthe relay can correspond to a second part of a disk rotation. Where thefirst state of the relay corresponds to a first half of the diskrotation and the second state of the relay corresponds to a second halfof the disk rotation, then a full rotation of the disk would encountertwo changes in state of the sensed value at pulse sensor 1310. As wouldbe appreciated, utility meters can be defined such that a differentnumber of state changes in the relay can be produced for a single diskrotation. Thus, while pulse sensor 1310 can measure the number ofchanges in the state of the relay at utility meter 1320 over a period oftime, pulse sensor 1310 would not know how many disk rotations actuallyoccurred at utility meter 1320 in that period of time. Without knowledgeof the number of disk rotations that actually occurred at utility meter1320, information about the amount of a utility service consumed wouldnot be available.

In the present disclosure, it is recognized that the same pulse sensorcan be used to measure relay transitions in many different types ofutility meters having different rates of correspondence between relaytransitions and disk rotations. In converting the measured number ofrelay transitions into useful information, a transformation function canbe defined to perform the conversion of sensor data into sensorinformation.

Consider a simple example of a utility meter that has four relaytransitions per disk rotation. In this example, a first transformationfunction (divide by four) can be a defined such that the number ofdetected relay state transitions by the pulse sensor is divided by fourto produce a corresponding number of disk rotations. The number of diskrotations could then be converted by a second transformation functioninto an actual consumption quantity of the utility measured by theutility meter. As would be appreciated, the combination of the first andsecond transformation function can be defined to match the particularcharacteristics of the utility meter being monitored to produce usefulinformation.

In the present disclosure, it is recognized that the definition of thetransformation function for a pulse sensor effectively representsanother form of remote configuration of the sensor module unit, whereinthe configuration need not be performed prior to installation of thesensor module unit. In fact, this level of configuration can beperformed without modification of the sensor module unit itself, furtherminimizing installation and maintenance costs. For example, if theutility meter at the monitored location is changed such that the numberof relay transitions per disk rotation changes, then the transformationfunction applicable to that particular sensor channel of data can bemodified without requiring a replacement or modification of the sensormodule unit at the monitored location.

Through the interaction by a user with user interface 1251, atransformation function for sensor “n” of the sensor module unitattached to port Y of wireless node 1230-X at monitored location 1210would be specified. The specification of the transformation function canthen be returned as a configuration command (communication 2) to hostsystem 1240. In one embodiment, a transformation function definition isstored in a database for retrieval and application by host system 1240to the sensor channel produced by sensor “n” of the sensor module unitattached to port Y of wireless node 1230-X. In one example, thetransformation function definition is stored in accordance with anidentifier based on a gateway identifier, a wireless node identifier, aport identifier and a sensor identifier.

In operation, host system 1240 would receive a sensor channel of datagenerated by sensor “n” in the sensor module unit attached to port Y ofwireless node 930-X. Host system 1240 would then retrieve the definitionof Transformation Function A stored in association with that sensorchannel of data, apply Transformation Function A to the sensor channelof data using processing component 1241, and produce a transformedsensor channel of data. The transformed sensor channel of data can thenbe stored and distributed by host system 1240 as usable sensorinformation.

As described, user interface 1251 on configuration station 1250 enablesa user to remotely configure a transformation function for every sensorin every sensor module unit attached to every wireless node at themonitored location. By this specification, effective configurationand/or reconfiguration of the sensor can be performed after installationof the sensors at the monitored location. The effective configurationand/or reconfiguration of the sensors through specification ofapplicable transformation functions enables the host system to generateusable information with minimal changes to the deployed wireless sensornetwork in the monitored location.

Another embodiment of the present disclosure can provide a machineand/or computer readable storage and/or medium, having stored thereon, amachine code and/or a computer program having at least one code sectionexecutable by a machine and/or a computer, thereby causing the machineand/or computer to perform the steps as described herein.

Those of skill in the relevant art would appreciate that the variousillustrative blocks, modules, elements, components, and methodsdescribed herein may be implemented as electronic hardware, computersoftware, or combinations of both. To illustrate this interchangeabilityof hardware and software, various illustrative blocks, modules,elements, components, methods, and algorithms have been described abovegenerally in terms of their functionality. Whether such functionality isimplemented as hardware or software depends upon the particularapplication and design constraints imposed on the overall system. Thoseof skill in the relevant art can implement the described functionalityin varying ways for each particular application. Various components andblocks may be arranged differently (e.g., arranged in a different order,or partitioned in a different way) all without departing from the scopeof the subject technology.

These and other aspects of the present disclosure will become apparentto those skilled in the relevant art by a review of the precedingdetailed disclosure. Although a number of salient features of thepresent disclosure have been described above, the principles in thepresent disclosure are capable of other embodiments and of beingpracticed and carried out in various ways that would be apparent to oneof skill in the relevant art after reading the present disclosure,therefore the above disclosure should not be considered to be exclusiveof these other embodiments. Also, it is to be understood that thephraseology and terminology employed herein are for the purposes ofdescription and should not be regarded as limiting.

What is claimed is:
 1. A system, comprising: a wireless node at amonitored location, the wireless node connected to a metering device viaa wired connection for receipt of metering signals from the meteringdevice; a gateway device configured to receive metering devicemeasurements via wireless communication with the wireless node; and ahost system having a plurality of servers at a location remote from themonitored location, one or more of the plurality of servers configuredto communicate with the gateway device via a communication network toreceive the metering device measurements, the one or more of theplurality of servers storing a transformation function in associationwith an identifier for a first of a plurality of sensor channels of datacollected by the gateway device, wherein the transformation functionincludes a meter conversion variable applied by the one or more of theplurality of servers to convert the first of the plurality of sensorchannels of data to a metering amount for a transformed sensor channelof metering data, the one or more of the plurality of servers furtherconfigured to transmit the transformed sensor channel of metering datato a customer wherein the one or more of the plurality of servers storesa second transformation function in association with the identifier forthe first of the plurality of sensor channels of data.
 2. The system ofclaim 1, wherein the wireless nodes includes a sensor module having aplurality of sensors for measuring signals from a plurality of meteringdevices, the sensor module connected to wireless transceiver module viaa serial communication interface.
 3. The system of claim 1, wherein themeter conversion variable is an integer used as a multiplier or dividerin the transformation function.
 4. The system of claim 1, wherein themetering device is one of a water meter, gas meter, and electricitymeter.
 5. The system of claim 1, wherein the metering signals are pulsesignals.
 6. The system of claim 1, wherein the first plurality of sensorchannels of data includes multiple sensor channels of data from thewireless node.
 7. The system of claim 1, wherein the one or more of theplurality of servers stores a second transformation function inassociation with the identifier for the first of the plurality of sensorchannels of data.
 8. A system, comprising: a database configured tostore a plurality of transformation functions in association with afirst of a plurality of sensor channels of data associated with awireless node at a monitored location the wireless node connected to ametering device via a wired connection for receipt of metering signalsfrom the metering device, wherein the wireless node communicates with agateway device via wireless communication; and one or more of aplurality of servers configured to communicate with the gateway devicevia a communication network, the one or more of the plurality of serversconfigured to apply the plurality of transformation functions to convertthe first of the plurality of sensor channels of data to a meteringamount to produce a transformed sensor channel of metering data, the oneor more of the plurality of servers further configured to transmit thetransformed sensor channel of metering data to a customer.
 9. The systemof claim 8, wherein the one or more of the plurality of servers areconfigured to transmit computer readable program code that enables acustomer device to render a user interface that enables the customer tospecify at least one of the plurality of transformation functions. 10.The system of claim 8, wherein the plurality of transformation functionsare stored in association with one or more of an identifier of thegateway device, an identifier of the wireless node, and an identifier ofa sensor in the wireless node.
 11. The system of claim 8, wherein atleast one of the plurality of transformation functions includes a meterconversion variable used as a multiplier or divider in thetransformation function.
 12. The system of claim 8, wherein the meteringsignals are puke signals.
 13. A method, comprising: receiving, by afirst of a plurality of servers, a specification of a meter conversionvariable for a sensor channel of data associated with a wireless node ata monitored location, the sensor channel of data associated withmetering signals received by the wireless node, wherein the sensorchannel of data is delivered by the wireless node to a gateway devicevia wireless communication; storing, by the first of the plurality ofservers, a plurality of transformation functions corresponding to thesensor channel of data, wherein a first of the plurality oftransformation functions is based on the meter conversion variable andis stored in association with an identifier associated with the sensorchannel of data; receiving, by one or more of the plurality of servers,metering signal measurements in the sensor channel of data;transforming, by the one or more of the plurality of servers, themetering signal measurements to a metering amount using the meterconversion variable in the first of the plurality of transformationfunctions; and transmitting the metering amount to the customer.
 14. Themethod of claim 13, wherein the monitored location is a building. 15.The method of claim 13, wherein the storing comprises storing the firstof the plurality of transformation functions in association with one ormore of an identifier of the gateway device, an identifier of thewireless node, and an identifier of a sensor in the wireless node. 16.The method of claim 13, further comprising transmitting a description ofa predefined transformation function to a customer device as an optionfor selection in a user interface.
 17. The method of claim 13, whereinthe meter conversion variable is an integer used as a multiplier ordivider in the transformation function.
 18. The method of dam 13,wherein the metering signal measurements are pulse signals.